Federated identity management for data repositories

ABSTRACT

A method and system for performing federated identity management are described. The method and system include receiving a communication for a data source at a wrapper. The wrapper includes a dispatcher and a service. The dispatcher receives the communication and is data agnostic. The communication corresponds to end user credentials for an end user. The method and system include providing the communication from the dispatcher to the data source and to the service. The method and system also use the service to authenticate the end user based on the end user credentials and utilizing federated identity management.

CROSS REFERENCE TO OTHER APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/733,013 entitled ARCHITECTURE HAVING A PROTECTIVE LAYER AT THEDATA SOURCE, BEHAVIORAL BASELINING FROM DATA SOURCE PERSPECTIVE ANDTOKENIZATION SUCH THAT ONLY AUTHORIZED APPLICATIONS CAN USE TOKENS filedSep. 18, 2018; to U.S. Provisional Patent Application No. 62/758,223entitled ARCHITECTURE HAVING A DATA SOURCE WRAPPER AND APP AGENT filedNov. 9, 2018; and to U.S. Provisional Patent Application No. 62/840,847entitled ARCHITECTURE HAVING A PROTECTIVE LAYER AT THE DATA SOURCE ANDTHAT PROVIDES QUERY ANALYSIS, FEDERATED IDENTITY MANAGEMENT ANDMULTIFACTOR AUTHENTICATION filed on Apr. 30, 2019, all of which areincorporated herein by reference for all purposes.

BACKGROUND OF THE INVENTION

Conventional security models protect data and electronic assets byproviding a secure perimeter around an organization. The secureperimeter includes not only the data sources, servers, and otheranalogous assets, but also clients employed by users of the assets.However, applications remain vulnerable, unscrupulous individuals maystill obtain copies of sensitive data and administration of the secureperimeter may be complex and expensive. In addition, data sources, suchas conventional databases and modern data repositories includingdistributed message queues, may not be configured for other types ofsecurity, such as tokenization of data and federated identitymanagement. Accordingly, an improved mechanism for providing securityfor data sources is desired.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is an exemplary embodiment of a system including a protectivelayer at the data source.

FIG. 2 is another exemplary embodiment of a system including aprotective layer at the data source.

FIG. 3 is another exemplary embodiment of a system including aprotective layer at the data source.

FIG. 4 is a flow chart depicting an exemplary embodiment of a method forauthenticating a client for a data source.

FIG. 5 is a flow chart depicting an exemplary embodiment of a method forperforming services for a client for a data source.

FIG. 6 is a flow chart depicting an exemplary embodiment of a method forperforming multi-factor authentication for a client for a data source.

FIG. 7 is a flow chart depicting an exemplary embodiment of a method forperforming federated identity management for a client for a data source.

FIG. 8 is a flow chart depicting another exemplary embodiment of amethod for authenticating a client for a data source using federatedidentity management.

FIG. 9 is a flow chart depicting an exemplary embodiment of a method foranalyzing and logging information related to queries of a data source.

FIG. 10 is a diagram depicting an exemplary embodiment of an abstractsyntax tree.

FIGS. 11A and 11B are flow charts depicting exemplary embodiments ofmethods for utilizing tokenization and/or encryption of sensitive data.

FIGS. 12A and 12B are flow charts depicting exemplary embodiments ofmethods for providing client information and for performing behavioralbaselining for clients.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

The systems and methods described herein provide a protection layer, orwrapper, that resides at and functions as a secure perimeter around adata source. Clients (e.g. applications and/or end users) communicatewith and are validated by the wrapper to access the data source.Compromised applications (including previously validated applications)may be denied access to the data source. This approach is in contrast tosecurity measures that place a perimeter around the entire organizationincluding the data source and applications. The methods and systems mayalso track an application's accesses of the data source to determine acontext/behavioral baseline for the application. For example, the typeof session, browser, APIs, IP address, query attributes etc. may be usedto determine a behavioral baseline for accesses of the data source.Subsequent accesses are compared to the baseline to determine whether acurrent query matches the baseline. If not, additionalvalidation/defense mechanisms may be employed. Application identity, orapplication fingerprinting, may be incorporated into this behavioralbaselining. In some aspects, data masking may also be employed. In datamasking, sensitive data are replaced by tokens or format preservingencryption having a similar form but without intrinsic meaning. Forexample, credit card or social security numbers may be replaced by adifferent number having the same number of digits. Tokens may also havean expiration time, requestor identification and other data used totrack tokens' use. Tokens are used unless/until the sensitive data areneeded (e.g. credit card number needed to process a transaction). If thesensitive data are needed, tokens are presented to the data vault andvalidated to obtain the sensitive data.

In some embodiments, a wrapper functions as a secure perimeter around adata source. The wrapper includes a dispatcher and a number of servicesthat communicate with the dispatcher. The dispatcher may be a Layer 4component that intercepts accesses of the data source. Both incomingaccesses and outgoing data may be intercepted by the dispatcher. Thedispatcher is data agnostic so can be deployed across a variety of datasources. The dispatcher may hold packets (step mode) or immediatelyforward packets to/from the data source (stream mode) but does notinspect the packets. The dispatcher also provides packets to theservices. The services perform deeper inspection of the packetsintercepted by the dispatcher. Services may provide one or morefunctions including but not limited to: authentication of theuser/requester of the data source, query analysis, multifactorauthentication, tokenization of data, rewriting, caching and behavioralbaselining (using collectors), federated identity management and otherfunctionality. In some embodiments, services may include Layer 7(application layer) components. For example, for authentication, theservice may inspect the user's credentials (e.g. user id and passwordand/or certificate) for that data source and only allow access to thedata source if the user's credentials are validated. One or more ofthese services can be used together. This approach is in contrast tosecurity measures that place a perimeter around the entire organizationincluding the data source and applications or which attempt to managethe data source/organization using Layer 7 components.

In addition to the wrapper at the data source, collectors may be used atsome/all of the clients using the data repository/data source.Collectors can be present for some or all clients having applicationsissuing queries to the data source. For example, collectors can beattached to applications for end users as well as in microservicesutilized by end users. A collector intercepts a communication (e.g. aquery or method call) from the application and examines the state of theapplication. For example, the type of session, get/put/post/deletecommands, APIs, IP address, query attributes, method calls, order ofqueries and/or other information may be detected by the collector. Theserepresent the context of the query, or state of the application/clientissuing the query. The collectors attach this context to the query. Inthe case of microservices/multiple applications pass a query before thequery is sent to a database. For example, one microservice may issue aquery and pass the query to a second microservice. The secondmicroservice may add to the query or issue an additional query. Thecollector for each microservice/application can obtain the context fromthat microservice/application. The collector also attaches the contextfrom that microservice/application to the query/queries. Thus, multiplecontexts may be obtained from multiple microservices/applications for asingle access of a data source. The query and context are passed to thewrapper when the data source is accessed. Over multiple accesses, thecontext can be used by the wrapper (e.g. a service) to determine thebehavior (sequence of states/contexts) for each application's accessesof the data source. A model of the behavior (e.g. a Hidden Markov Model)can provide a behavioral baseline. Subsequent accesses are compared tothe behavioral baseline to determine whether a current query matches thebehavioral baseline. If not, additional validation/defense mechanismsmay be employed. For example, access to the data source can be refusedand/or multifactor authentication invoked. Collectors and/or behavioralbaselining may be used in conjunction with other services.

Requests regarding sensitive data can be sent to atokenization/encryption service by the dispatcher. The service replacessensitive data with tokens/format preserving encryption (FPE), oranalogous data that is without intrinsic meaning. What is used (tokensor FPE) is configurable on the attribute level. For example, for creditcard numbers of a user, FPE can be used. For the social security numberof the same user, a token can be used. In some embodiments, the requestto store sensitive information can be provided to the service and thevalue encrypted before storage in the data store. A request to obtainthe number can be provided to the service which can decrypt/detokenizeif the requester is authorized. Alternatively, the token/FPE can beprovided in response to the request. Tokens/FPE can have an expirationtime, requestor identification or other information. Tokens are usedunless/until the sensitive data are needed (such as a credit card numberneeded to process a transaction). If the sensitive data are needed,tokens are presented to the data vault and validated to obtain thesensitive data. This validation may require additional, more trustedmechanisms for ensuring the security of the sensitive data. Tokenizationcan be used in conjunction with behavioral baseline/collectors,multifactor authentication and/or other services.

Multifactor authentication may also be performed using a service. Insome embodiments, the dispatcher is placed in step mode, to hold packetsinstead of directly forwarding to a data source. The dispatcher alsoprovides packets to the service, which controls multi-factorauthentication. The service performs multifactor authentication (e.g.requiring a code to be sent to a separate device and input) or accessesa third party multifactor authentication service. Once multifactorauthentication is completed, the dispatcher is placed in stream mode,allowing the user to communicate with the data source. Thus, the dataagnostic dispatcher can provide multifactor authentication across anumber of different data sources, such as databases that do nottraditionally support multifactor authentication.

The dispatcher can forward requests/queries to an analyzer service thatperforms query analysis. The analyzer service examines/parses thequeries and emits a structure that describes the query. In someembodiments, the structure is an abstract syntax tree. However, otherstructures may be used. The structure can be used to determine whetherthe query represents an attack, (e.g. to obtain unauthorizedinformation) to determine whether the query will adversely affectperformance. For example, queries which include wildcards or tautologiesin users' names can result in exfiltration of sensitive information.Queries that are missing a where clause can adversely affects databaseperformance. Such queries may be identified. The packet including thequery can then be stopped or the query can be canceled. Further, thestructure emitted by the query analyzer may be used to log or otherwisestore information about the queries. For example, the structure may beused to identify and log features of the query that may be of interest.Such information may be used in conjunction with analytics to examineuse of the data source. In some embodiments, the information regardingqueries that is logged can be indexed and may include only informationpreviously identified as sensitive. For example, the tables, columns intables, and data entries corresponding to the identified sensitiveinformation may be logged. Further, such information redacted so thatcertain information, such as names and/or social security numbers, arenot included in the log.

Another service provided may include query rewriting, which may be usedwith query analysis. Queries that may adversely affect performance canbe rewritten. For example, a limit may be added so that too many resultsare not returned, a tautology removed, and/or other portions of thequery rewritten to improve performance.

A service can be used for federated identity management (for example vialightweight directory access protocol (LDAP)). An end user requestsaccess to the data repository/database and provides the directory accesscredentials via the wrapper. The dispatcher provides the request to aservice controlling federated identity management. The wrapper/servicedetermines whether the end user exists on a directory access server(e.g. an LDAP server), authenticates the end user's credentials on thedirectory access server and determines the groups to which the end userbelongs. The service uses the group information to access the datarepository as a proxy for the end user.

A method and system for performing at least one service are disclosed.The method and system include receiving a communication for a datasource at a wrapper. The wrapper includes a dispatcher and at least oneservice. The dispatcher receives the communication and is data agnostic.The method and system also include providing the communication from thedispatcher to the data source and to the at least one service. The atleast one service inspects the communication and may perform additionalfunctions. In some embodiments, the dispatcher is an open systemsinterconnection (OSI) Layer 4 dispatcher and the service(s) include OSILayer 7 service(s). In some embodiments, the method and system alsoinclude performing at least one function by the at least one servicebased on the communication. The at least one function may include one ormore of authentication services, multifactor authentication,tokenization of data, encryption of data, query analysis, behavioralbaselining, and federated identity management. For example, thecommunication may be generated at a client and service(s) may include anauthentication service. In such embodiments, the method and systemfurther include determining whether the client is authorized to accessthe data source using the authentication service and preventing accessto the data source if the client is not authorized to access the datasource. For example, the communication may be provided to the datasource only if the authentication service determines the client isauthorized to access the data source. In some embodiments, thecommunication to the data source from the dispatcher and recalled beforeprocessing by the data source if the authentication service determinesthe client is not authorized to access the data source. In someembodiments, the communication is generated at a client and includes afirst communication. The service(s) include an authentication servicethe dispatcher is in a step mode for the first communication from theclient. In such embodiments the first communication may be provided tothe authentication service without forwarding the first communication tothe data source (step mode). The authentication service may use thefirst communication to determine whether the client is authorized toaccess the data source. If it is determined that the client is notauthorized to access the data source, access to the data source by theclient may be prevented by terminating a connection to the client. If itis determined that the client is authorized, then the firstcommunication is provided from the dispatcher to the data source. Thedispatcher is also placed in a stream mode. Upon receiving additionalcommunication(s) from the client, the dispatcher, automatically forwardsthe at least one additional communication from the dispatcher to thedata source.

A method and system that may utilize behavioral baselining aredisclosed. The method and system include receiving, at the wrapper, acommunication and a context associated with the communication from aclient. The communication is for a data source. The wrapper includes thedispatcher and the service. The method and system also include providingthe context from the dispatcher to the service. In some embodiments, themethod and system use the service to compare the context to a behavioralbaseline for the client. The behavioral baseline incorporates aplurality of contexts previously received from the client. The methodand system also permit the client access the data source only if thecontext is consistent with the behavioral baseline. The behavioralbaseline may also be updated based on the context. In some embodiments,the communication is intercepted at the client using a collector. Thecollector determines the context of the client and attaches the contextto the communication. In some embodiments, the method and system includereceiving, at the dispatcher and from the client, additionalcommunication(s) and additional context(s) associated with theadditional communication(s). The additional communication(s) are for thedata source. The additional context(s) are provided from the dispatcherto the service. The service compares the context and additionalcontext(s) to the behavioral baseline for the client. In someembodiments, the client is allowed to access the data source only if thecontext and the additional context(s) are consistent with the behavioralbaseline. In some embodiments, the method and system also includereceiving additional context(s) associated with the communication fromadditional client(s). The additional context(s) are also provided fromthe dispatcher to the service. In such embodiments, the service comparesthe context and the additional context(s) to the behavioral baseline forthe client.

A method and system for anonymizing data are disclosed. The method andsystem include receiving, at the wrapper, a request to store data in adata source. The method and system also include providing the requestfrom the dispatcher to the at least one service and anonymizing, at theservice(s), the data to provide anonymized data. The anonymized data maybe provided to the data source. In some embodiments, the requestincludes the data and additional data. In such embodiments, theanonymizing further includes identifying the data to be anonymized. Theanonymizing may include tokenizing and/or encrypting the data. Thetokenizing and/or encrypting may be selected based upon a policy for thedata. In some embodiments, the encryption uses format preservingencryption. In some embodiments, the method and system further includereceiving, from a requester, an access request for the data. Therequester is authenticated. If the requester is authorized to receivethe data, the method and system include de-anonymizing the anonymizeddata and providing de-anonymized data to the requester. If the requesteris authorized to receive the anonymized data, the method and systeminclude providing the anonymized data.

A method and system for performing authentication are described. Themethod and system include receiving, from a client, a communication fora data source at the wrapper. The communication is provided from thedispatcher to the service. The service determines whether the client isauthorized to access the data source. In some embodiments, the servicedetermines whether the client is authorized by calling a multi-factorauthentication (MFA) utility. The method and system also includereceiving, from the MFA utility, a success indication. The successindication indicates whether authentication by the MFA utility issuccessful. In some embodiments, the MFA utility is a third-party MFAutility. The method and system may also include preventing access to thedata source if the success indication indicates that the authenticationis unsuccessful. Preventing access may include providing thecommunication to the data source from the dispatcher and recalling thecommunication before processing by the data source if the authenticationindication indicates the authentication is unsuccessful. In someembodiments, the communication includes a first communication and thedispatcher is in a step mode for the first communication. In suchembodiment, the preventing access may include providing the firstcommunication to the service without forwarding the first communicationto the data source. Preventing access to the data source may includeterminating a connection to the client if the success indicationindicates that the authentication is unsuccessful. In addition, thefirst communication may be forwarded from the dispatcher to the datasource if the success indication indicates that the authentication issuccessful. The dispatcher may be placed in a stream mode if the successindication indicates that the authentication is successful. At least oneadditional communication from the client may be received at thedispatcher. Such additional communications are automatically forwardedfrom the dispatcher to the data source if the success indicationindicates that the authentication is successful. In some embodiments,the dispatcher is an open systems interconnection (OSI) Layer 4dispatcher and wherein the at least one service includes at least oneOSI Layer 7 service.

A method and system for performing query analysis are described. Themethod and system include receiving a query for a data source at thewrapper. The method and system also include providing the query from thedispatcher to the data source and to the service. The query is analyzedusing the service. In some embodiments, analyzing the query furtherincludes parsing the query, providing a logical structure based on thequery and analyzing the logical structure. In some embodiments, a log isprovided based on the logical structure. The log may also be analyzed.The method and system may include receiving at least one of anidentification of sensitive data and sensitive data policies. In somesuch embodiments, providing the log further includes redacting a portionof the log based on the sensitive data policies and the identificationof the sensitive data. The method and system may prevent access to thedata source if the analysis of the query indicates the query is anattack. In some embodiments, the method and system rewrite the query ifthe analysis of the query indicates the query adversely affectsperformance. In some embodiments, the analysis of the query indicatesthat data for a response to the query is in a cache. In suchembodiments, the method and system may provide the data from the cache.

A method and system for performing federated identity management aredescribed. The method and system include receiving a communication for adata source at a wrapper. The wrapper includes a dispatcher and aservice. The dispatcher receives the communication and is data agnostic.The communication corresponds to end user credentials for an end user.The method and system include providing the communication from thedispatcher to the data source and to the service. The method and systemalso use the service to authenticate the end user based on the end usercredentials and utilizing federated identity management. In someembodiments, the method and system also include accessing the datasource by the wrapper as a proxy for the end user if the end user isauthenticated using the federated identity management. The end useractivities for the data source may also be logged. In some embodiments,authenticating the end user includes providing the end user credentialsto a federated identity management data source. The federated identitymanagement data source may be searched for group(s) to which the enduser belongs. In some embodiments, a read only binding of the service tothe federated identity management data source is performed. In suchembodiments, the federated identity management data source may besearched for the end user using the read only binding. If the end useris authenticated, the method and system may include binding the serviceto the federated identity management data source as a proxy for the enduser. Access to the data source may be prevented if the end user is notauthenticated utilizing the federated identity management.

FIG. 1 is a diagram depicting an exemplary embodiment of a system 100utilizing a protective layer between clients and data sources. System100 includes data sources 102 and 104, clients 106-1, 106-2 and 106-3(collectively clients 106) and wrapper 110. Although two data sources102 and 104, three clients 106 and one wrapper 110 are shown, in anotherembodiment, different numbers of data sources, clients, and/or wrappersmay be used. Data sources 102 and 104 may be databases, data stores,data vaults or other data repositories. Clients 106 may be computersystems for end users and/or include applications which providerequests, or queries, to data sources 102 and 104. Clients 106 may bepart of the same organization as the data sources 102 and 104 or may beoutside users of data sources 102 and 104. For example, clients 106 anddata sources 102 and 104 may be part of the same business organizationcoupled by an internal network. In other embodiments, clients 106 may beoutside users of data sources 102 and 104 connected to wrapper 110and/or data sources 102 and/or 104 via the Internet or other externalnetwork. In some embodiments, some clients 106 may be external users ofdata sources 102 and 104 while other clients 106 are part of the sameorganization as data sources 102 and 104.

Wrapper 110 provides a protective layer between clients 106 and datasources 102 and 104. Wrapper 110 is configured such that its operationis data agnostic. Thus, wrapper 110 may be used with data sources 102and 104 that have different platforms, are different databases, or areotherwise incompatible. Wrapper 110 is so termed because althoughdepicted as residing between clients 106 and data sources 102 and 104,wrapper 110 may be viewed as enclosing, or forming a secure perimeteraround data sources 102 and 104. Stated differently, clients 106 cannotbypass wrapper 110 in order to access data sources 102 and 104 in atleast some embodiments. For example, a security group may be created fordata sources 102 and 104. Dispatcher 112/wrapper 110 may be the onlymember of the security group. Thus, clients 106 may access data sources102 and 104 only through wrapper 110. Clients 106 connecting to wrapper110 may be internal or external to an organization. Therefore, wrapper110 need not reside at the perimeter of an organization or network.Instead, wrapper 110 may reside at data sources 102 and 104. Stateddifferently, wrapper 110 may provide the final or only security forrequests for data source 102 and 104 and need not provide security forother components of the organization. Thus, requests made by clients 106may be passed directly from wrapper 110 to data sources 102 and 104 viaa network.

Wrapper 110 provides security and other services for data sources 102and 104 and clients 106. To do so, wrapper 110 includes dispatcher 112and services 114-1 and 114-2 (collectively services 114). Dispatcher 112is data agnostic and in some embodiments is a transport layer component(e.g. a component in Layer 4 of the Open Systems Interconnection (OSI)model). Dispatcher 112 thus performs limited functions and is not aLayer 7 (application layer) component. In particular, dispatcher 112receives incoming communications from clients 106. As used herein, acommunication includes a request, a query such as a SQL query, or othertransmission from clients 106 to access data source 102 or 104.

Dispatcher 112 also provides the requests to the appropriate datasource(s) 102 and/or 104 and the appropriate service(s) 114-1 and/or114-2. However, dispatcher 112 does not inspect incoming communicationsfrom clients 106 other than to identify the appropriate data source(s)102 and/or 104 and corresponding service(s) 114 for the communication.Dispatcher 112 does not make decisions as to whether communications areforwarded to a data source or service. For example, a communication froma client 106 may include a header indicating the data source 102 desiredto be accessed and a packet including a query. In such a case,dispatcher 112 may inspect the header to identify the data source 102desired to be accessed and forwards the packet to the appropriate datasource 102. Dispatcher 112 also provides the packet to the appropriateservice(s) 114. However, dispatcher 112 does not perform deep inspectionof the packet. Instead, the appropriate service(s) inspect the packet.In some embodiments, dispatcher 112 provides the communication to theappropriate service(s) 114 by storing the packet and providing toservice(s) 114 a pointer to the storage location.

In some embodiments, dispatcher 112 holds communications (e.g. packets)while service(s) 114 perform their functions. In other embodiments,dispatcher 112 directly forwards the communications to data source(s)102 and/or 104 and services 114 separately perform their functions. Insome embodiments, whether dispatcher 112 holds or forwardscommunications depends upon the mode in which dispatcher 112 operates.For example, in a step mode, dispatcher 112 may store some or all of thecommunication from client 106-1 without forwarding the communication todata sources 102 and 104. In such a mode, dispatcher 112 only forwardsthe communication to a data source if instructed to do so by theappropriate service 114 or if placed into stream mode by the appropriateservice 114. Although not forwarding the communication to a data source,dispatcher 112 does provide the communication to service 114-1, forexample for client 106-1 to be authenticated and/or for other functions.If client 106-1 is authenticated, dispatcher 112 may be placed in streammode by service 114-1. Consequently, dispatcher 112 forwards thecommunication to the appropriate data source(s) 102. Because dispatcher112 is now in stream mode, subsequent communications from client 106-1may then be forwarded by dispatcher 112 directly to the appropriate datasource(s) 102 and/or 104, even if the subsequent communications are alsoprovided to a service 114 for other and/or additional functions. Thus,dispatcher 112 may provide the communication to the data source(s) asreceived/without waiting for a response from a service 114.

In some embodiments, responses from data source(s) 102 and/or 104 arealso inspected by wrapper 110 and provided to clients 106 only if theresponses are authorized. As used herein, a response from a data sourcemay include data or other transmission from the data source to theclient requesting access. In other embodiments, responses from datasource(s) 102 and/or 104 may bypass wrapper 110 and be provided directlyto clients 106. This is indicated by the dashed line from data source104 to client 106-1. In the embodiment shown, therefore, data source 104may bypass wrapper 110 and provide responses directly to client 106-1.

Services 114 provide security and other functions for data sources 102and 104 and clients 106. For example, services 114 may include one ormore of authentication, query analysis, query rewriting, caching,tokenization and/or encryption of data, caching, advanced or multifactorauthentication, federated identity management, and/or other services.Further, one or more of the services described herein may be usedtogether. Services 114 perform more functions than dispatcher 112 andmay be application layer (Layer 7) components. In contrast to dispatcher112, services 114 may perform a deeper inspection of communications fromclients 106 in order to provide various functions. The services 114performing their functions may thus be decoupled from forwarding ofcommunications to data source(s) 102 and/or 104 by dispatcher 112. If aclient or communication is determined by a service 114 to beunauthorized or otherwise invalid, the communication may be recalled, orcanceled, from data source(s) 102 and/or 104 and connection to theclient terminated. The communication may be recalled despite thedecoupling of tasks performed by services 114 with forwarding ofcommunications by dispatcher 112 because data sources 102 and 104typically take significantly more time to perform tasks than services114. The time taken by data source 102 and 104 may be due to issues suchas transmission over a network from wrapper 110 to data sources 102 and104, queues at data sources 102 and 104, and/or other delays.

In some embodiments, services 114 may perform authentication. Forexample, suppose service 114-1 validates credentials of clients 106 fordata sources 102 and 104. In some such embodiments, service 114-1 maysimply employ a username and password combination. In other embodiments,multifactor authentication (MFA), certificates and/or other higher levelauthorization is provided by one or more services 114. Suchauthentication is described herein. However, dispatcher 112 may still bea data agnostic component, such as a Layer 4 component.

In some embodiments, this separation of functions performed bydispatcher 112 and services 114 may be facilitated by routines or otherlightweight process(s). For example, a client such as client 106-2 mayrequest access to data source 104 via a particular port. Wrapper 110 mayutilize listener(s) (not shown in FIG. 1) on the ports to identifyrequests for data sources 102 and 104. In response to the request foraccess, a connection to the client 106-2 is established for the wrapper110 on that port and a routine corresponding to the connectiongenerated. In some embodiments, the routine is responsible for thatconnection only. The communication from client 106-2 is also provided todispatcher 112. Dispatcher 112 provides the communication to theappropriate service(s) 114 for authentication, for example via a messagebus (not shown in FIG. 1). Dispatcher 112 may hold (in step mode) orforward (in stream mode) the communication to the data source(s) 102and/or 104. If client 106-2 is not authenticated or is later determinedby service(s) 114 to be unauthorized, then the service(s) 114 indicatesthis to dispatcher 112. For example, service(s) 114 may provide amessage to dispatcher 112 via the message bus that client 106-2 is notauthorized/that the corresponding routine has an unauthorizedconnection. Dispatcher 112 communicates with the corresponding routine,which terminates the connection to client 106-2. Thus, connections toclients 106 may be securely managed using data agnostic, Layer 4dispatcher 112.

Using system 100 and wrapper 110, data sources 102 and 104 may besecured and other features may be provided via service(s) 114. Becauseof the use of data agnostic dispatcher 112, wrapper 110 may functionwith a variety of data sources 102 and 104 that do not share a platformor are otherwise incompatible. Deployment of wrapper 110, for exampleeither in the cloud or on premises, does not require changes in existingcode. Consequently, implementation of wrapper 110 may be seamless andrelatively easy for developers. Further, wrapper 110 need not protectevery component within a particular organization. Instead, only selecteddata sources may be protected. Use of services 114 for security asdescribed herein may be both more effective at securing sensitive dataand less expensive because data sources may not significantly increasein number even when the number of applications that access the datasources grows significantly. Further, utilizing services 114, the levelof security and/or functions provided by wrapper 110 may differ fordifferent data sources. Additional functionality may also be provided byservices 114.

FIG. 2 is a diagram depicting another exemplary embodiment of a system200 utilizing a protective layer between clients and data sources.System 200 is analogous to system 100 and includes components that arelabeled similarly. System 200 indicates that multiple wrappers havingdifferent services may be used. Thus, system 200 includes data sources202-1, 202-2 (collectively 202) and 204, clients 206-1, 206-2 and 206-3(collectively clients 206) and wrappers 210A and 210B (collectivelywrappers 210). Although three data sources 202-1, 202-2 and 204, threeclients 206 and two wrappers 210 are shown, in another embodiment,different numbers of data sources, clients, and/or wrappers may be used.Data sources 202-1, 202-2 and 204 and clients 206 are analogous to datasources 102 and 104 and clients 106, respectively. Wrappers 210A and210B are analogous to wrapper 110. Thus, wrapper 210A includesdispatcher 212A and services 214-1A and 214-2A (collectively services214A). Similarly, wrapper 210B includes dispatcher 212B and services214-1B, 214-2B and 214-3B (collectively services 214). Services 214A maydiffer from or be included in services 214B. Wrapper 210A controlsaccesses to data sources 202, while wrapper 210B controls accesses todata source 204 in a manner analogous to described elsewhere herein. Ingeneral, one wrapper having multiple services may function for all thedata sources in an organization. However, as depicted in FIG. 2, nothingprevents the use of multiple wrappers. Further, although wrappers 210Aand 210B are shown as controlling access to different data sources 202and 204, in other embodiments, wrappers may control the same datasource. For example, in another embodiment, wrapper 210B might serveboth data source 202-1 and data source 204.

FIG. 3 is a diagram depicting another exemplary embodiment of a system300 utilizing a protective layer between clients and data sources.System 300 is analogous to systems 100 and 200 and includes componentsthat are labeled similarly. System 300 also includes collector 320-1,320-2 and 320-3 (collectively collectors 320). Thus, system 300 includesdata sources 302 and 304, clients 306-1, 306-2 and 306-3 (collectivelyclients 306) as well as client 306-4 and wrapper 310. Although two datasources 302 and 304, four clients 306 and one wrapper 310 are shown, inanother embodiment, different numbers of data sources, clients, and/orwrappers may be used. Data sources 302 and 304 and clients 306 areanalogous to data sources 102 and 104 and clients 106, respectively.Wrapper 310 is analogous to wrapper 110. Thus, wrapper 310 includesdispatcher 212 and services 314-1, 314-2, 314-3, 314-4 and 314-5(collectively services 314). Wrapper 310 controls accesses to datasources 302 and 304. Also shown are utilities 330-1 and 330-2 that mightbe used by services 314. For example, service 314-1 might performauthentication and multifactor authentication using utility 330-1.Service 314-6 may perform federated identity management using utility330-2. Other and/or additional utilities may be used in connection withsystem 300, as well as with system(s) 100 and/or 200. Service 314-2might perform query analysis as described herein. Service 314-3 mightperform behavior modeling based on inputs from collectors 320. Service314-4 may perform tokenization and/or encryption of sensitive data.Service 314-5 may rewrite queries based on the analysis performed byservice 314-2. Alternatively, service 314-2 might also rewrite queries.Thus, service 314-5 might perform another function such as caching.Other services not described herein may also be provided. Two or moreservices may be used together in some embodiments

Collectors 320 reside on some clients 306. In some embodiments, each ofthe clients 306 includes a collector. In other embodiments, as shown inFIG. 3, not all clients 306 include a collector. In some embodiments,none of clients 306 includes a collector. For example, clients 306 mayinclude end users, applications, and/or microservices utilized by endusers. Thus, clients 306 may pass communications to each other prior tothe communication being provided to wrapper 310. This is indicated bydotted line between client 306-2 and client 306-3. Collectors 320intercept communications from clients 306 and append onto thecommunication a state of the client/application issuing thecommunication. For example, collector 320-1 may intercept a query ormethod call from the application on client 306-1 and examine the stateof the application. The type of session, get/put/post/delete commands,APIs, IP address, query attributes, method calls, order of queries etc.may be detected by collector 306-1. These represent the context of thequery/communication. Collectors 320 attach this context to thequery/communication from the corresponding clients 306. In the case ofmicroservices/multiple applications passing a query before the query issent to a data source, the collectors 320 for each of themicroservice/applications 306 may apply the context from thatmicroservice/application. For example, a query passed from client 306-2to client 306-3 and then to wrapper can include a first context providedby collector 320-2 and a second context provided by collector 320-3. Ifone or more of clients 306 being passed a query does not include acollector, then that client simply does not attach the context from theclient. For example, if a query is passed from client 306-1 to client306-4, then to client 306-3, a first context from collector 320-1 and asecond context from collector 320-3 are attached to the query. In suchembodiments, no context is attached by client 306-4 because no collectoris present for client 306-4. The query and context(s) are passed towrapper 310 when data source 302 or 304 is accessed. Over multipleaccesses, the contexts can be used by wrapper 310 (e.g. a service suchas service 314-3) to determine the behavior (sequence ofstates/contexts) for each application's accesses of data source(s) 302and/or 304. A model of the behavior (e.g. using a Hidden Markov Model)can provide a behavioral baseline. Subsequent accesses are compared tothe baseline by service 314-3 to determine whether a currentquery/communication matches the baseline. If not, additionalvalidation/defense mechanisms may be employed. For example, theconnection may be terminated as described herein, access to data source302 and/or 304 may be otherwise denied and/or additional forms ofvalidation such as MFA may be utilized via services 314.

System 300 may provide the benefits of systems 100 and/or 200. Inaddition, system 300 may improve security via collectors 320. Further,end-to-end visibility, from clients 306 to data sources 302 and 304, maybe provided via wrapper 310. Thus, performance of system 300 may beimproved.

FIG. 4 is a flow chart depicting an exemplary embodiment of method 400for authenticating a client for a data source. Method 400 is describedin the context of system 100. However, method 400 may be used inconnection with other systems including but not limited to systems 200and 300. For simplicity, certain steps of method 400 are depicted.Method 400 may include other and/or additional steps and substeps.Further, the steps of method 400 may be performed in another orderincluding performing portions or all of some steps in parallel. Method400 may be carried out each time a client commences a session forcommunication with a data source.

Dispatcher 112 of wrapper 110 receives a communication requesting accessto one or more data sources from a client, at 402. For example,dispatcher 112 may receive a communication requesting access to datasource 102 from client 106-1. The communication may be received atdispatcher 112 after a connection between wrapper 110 and client 106-1is established and a corresponding routine or other correspondinglightweight process generated. In addition to identifying data source102 and client 106-1, the request may also include credentials forclient 106-1. In some embodiments, at the start of method 400,dispatcher 112 is in step mode. At 404, therefore, dispatcher 112provides the communication from client 106-1 to service 114-1, whichperforms authentication. For example, dispatcher 112 may send thepayload of the communication to service 114-1 via a message bus (notseparately labeled in FIG. 1). However, because dispatcher 112 is instep mode, dispatcher 112 does not also forward the communication to therequested data source 102. Further, because dispatcher 112 is a dataagnostic component such as a Layer 4 component, dispatcher 112 does notperform a deeper inspection of the communication. Instead, dispatcher112 simply holds (e.g. stores) the communication because dispatcher 112is in step mode. If dispatcher 112 were in stream mode, dispatcher 112would also forward the packet to the appropriate data source 102.

Service 114-1 performs authentication of client 106-1, at 406. In someembodiments, a certificate and/or other credentials such as a usernameand password may be used to perform authentication. In some embodiments,MFA (described in further detail below) may be used. In addition, ifcollectors such as collectors 320 are present in the system, the contextof the communication provided by client 106-1 may be used inauthentication at 406. For example, the context appended to thecommunication by a collector 320 may be compared to a behavior baselinemodeled by system 100 from previous communications by client 106-1 todetermine whether the context sufficiently matches previous behavior.Other and/or additional authentication mechanisms may be used in someembodiments.

If the client requesting access is not authenticated, then access to thedata source is prevented, at 408. For example, the routine correspondingto the connection with client 106-1 may be notified and the connectionterminated. Other mechanisms for preventing access may also be used. Thecommunication held by dispatcher 112 is also discarded. In otherembodiments, if dispatcher 112 had forwarded the communication to datasource 102, then the communication is recalled at 408.

If the client is authenticated, then at 410, dispatcher 112 is placed instream mode at 410. As a result, the communication being held isforwarded to the selected data source 102 at 410. In addition, futurecommunications corresponding to the authenticated connection with client106-1 are forwarded to the selected data source 102 and appropriateservice(s) 114, at 412. For example, service 114-1 may provide a messageto dispatcher 112 changing dispatcher 112 from step mode to stream modeat 410. Consequently, dispatcher 112 also forwards the communication tocorresponding data source 102. Future communications received atdispatcher 112 from client 106-1 via the same connection may be bothprovided to one of the services 114 and to the selected data source 102.Thus, clients 106 are allowed to request and receive data from datasource 102. However, authentication may still continue. For example,behavioral baselining described herein, periodic requests to revalidatecredentials or other mechanisms may be used, at 414. If client 106-1loses its authentication, then communications from the client to theselected data source may be recalled and further access to the datasource blocked, at 414. For example, the routine responsible for theconnection to client 106-1 may be notified and the connectionterminated. Thus, connection to clients 106 may be securely managedusing dispatcher 112 that is a data agnostic component, such as a Layer4 component.

Using method 400, data sources 102 and 104 may be secured. Because ofthe use of data agnostic dispatcher 112, wrapper 110 may function with avariety of data sources 102 and 104 that do not share a platform or areotherwise incompatible. Deployment of wrapper 110, for example either inthe cloud or on premises, may require no change in existing code.Consequently, implementation of wrapper 110 may be seamless andrelatively easy for developers. Further, wrapper 110 need not protectevery component within a particular organization. Instead, only selecteddata sources may be protected. Use of services 114 for security asdescribed herein may be both more effective at securing sensitive dataand less expensive because data sources may not significantly increasein number even when the number of applications that access the datasources grows significantly. Further, utilizing services 114, the levelof security and/or functions provided by wrapper 110 may differ fordifferent data sources.

FIG. 5 is a flow chart depicting an exemplary embodiment of method 500for performing one or more services for a client and a data source.Method 500 is described in the context of system 100. However, method500 may be used in connection with other systems including but notlimited to systems 200 and 300. For simplicity, certain steps of method500 are depicted. Method 500 may include other and/or additional stepsand substeps. Further, the steps of method 500 may be performed inanother order including performing portions or all of some steps inparallel. In some embodiments, method 500 may be considered to beoperable once authentication of the client is completed and dispatcher112 is in stream mode.

Dispatcher 112 of wrapper 110 receives a communication from a client, at502. For example, dispatcher 112 may receive a communication from client106-2 with a query for data source 104. One or more services 114 aredesired to be used with the communication. Therefore, dispatcher 112provides the communication from client 106-2 to service(s) 114, at 504.In addition, dispatcher 112 forwards the communication to the requesteddata source 104 at 504. Stated differently, dispatcher 112 provides therelevant portions of the communication to both the desired datasource(s) and service(s). Because dispatcher 112 is a data agnosticcomponent such as a Layer 4 component, dispatcher 112 does not perform adeeper inspection of the communication. Instead, dispatcher 112 simplyforwards the communication both to the desired data source(s) 102 and/or104 and to service(s) 114 for further processing.

The desired functions are provided using one or more of the services114, at 506. This may include inspecting the communication as well ascompleting other tasks. For example, at 506, services 114 may be usedfor authentication of various types, query analysis, federated identitymanagement, behavioral modeling, query rewriting, caching, tokenizationor encryption of sensitive data and/or other processes. Services 114 maythus be Layer 7 components. However, tasks performed by services 114 aredecoupled from forwarding of the communication to data sources bydispatcher 112.

Using system method 500 and wrapper 110, data sources 102 and 104 may besecured and other features may be provided via service(s) 114. Becauseof the use of data agnostic dispatcher 112, wrapper 110 may functionwith a variety of data sources 102 and 104 that do not share a platformor are otherwise incompatible. Functions performed by services 114 aredecoupled from forwarding of communications to the data sources bydispatcher 112. Thus, a variety of features may be provided for datasources 102 and 104 without adversely affecting performance of datasources 102 and 104. Consequently, performance of system 100 may beimproved.

FIG. 6 is a flow chart depicting an exemplary embodiment of method 600for performing multifactor authentication (MFA) for a client and a datasource. Method 600 is described in the context of system 300. However,method 600 may be used in connection with other systems including butnot limited to systems 100 and 200. For simplicity, certain steps ofmethod 600 are depicted. Method 600 may include other and/or additionalsteps and substeps. Further, the steps of method 600 may be performed inanother order including performing portions or all of some steps inparallel. In some embodiments, method 600 may be considered to be usedin implementing 406 and/or 506 of method 400 and/or 500. For thepurposes of explanation, suppose service 314-1 provides multi-factorauthentication. Method 600 may be considered to start after the MFAservice 314-1 receives the communication from dispatcher 312. Further,dispatcher 312 may be in step mode at the start of method 600. Thus,dispatcher 312 may hold the communication instead of forwarding thecommunication to data source(s). In other embodiments, dispatcher 312may be in stream mode. Dispatcher 312 may, therefore, may also providethe communication to the appropriate data sources. MFA may be performedin addition to other authentication, such as certificate or useridentification/password based authentication, performed by service 314-1or another service. Although described in the context of authenticationfor access to a single data source, in some embodiments, method 600 maybe used to authenticate client(s) for multiple data sources.

Service 314-1 calls a MFA utility 330-1, at 602. The MFA utility 330-1contacted at 602 may be a third party MFA such as DUO. Alternatively,the MFA utility 330-1 may be part of the organization to which datasource(s) 302 and/or 304 belong. MFA utility 330-1 performs multi-factorauthentication for the requesting client, at 604. For example, supposeend user of client 306-2 has requested access to data source 304. Theuser identification and password may have been validated by service314-1. At 602, the MFA utility 330-1 is called. Thus, the end user isseparately contacted by MFA utility 330-1 at 604 and requested toconfirm the user's by the MFA facility. For example, the end user may berequired to enter a code or respond to a prompt on a separate device. Aspart of 604, service 314-1 is informed of whether the multi-factorauthentication by MFA utility 330-1 is successful. Stated differently,as part of 604, service 314-1 receives from MFA utility 330-1 a successindication. The success indication informs MFA utility 330-1 of whetheror not MFA authentication was successful.

If the multi-factor authentication by MFA utility 330-1 is successful,then service 314-1 instructs dispatcher 312 to forward communications tothe requested data source 304, at 606. In some embodiments, in responseto receiving a positive success indication (i.e. that MFA authenticationis successful), service 314-1 directs dispatcher 312 to forwardcommunications to the requested data source 304. In some embodiments,dispatcher 312 is instructed to change from step mode to stream mode at606. Thus, subsequent communications may be provided both to the datasource 304 and one or more service(s) 314. In other embodiments,dispatcher 312 is simply allowed to continue forwarding communicationsto data source 304 at 606. If, however, multifactor authentication wasunsuccessful, service 314-1 instructs dispatcher 312 to prevent accessto the requested data source 304, at 608. For example, in response toreceiving a negative success indication (i.e. that MFA authentication isunsuccessful), service 314-1 directs dispatcher 312 to prevent access tothe requested data source 304. In response, dispatcher 312 may instructthe corresponding routine to terminate the connection with therequesting client 106. If the communication has already been forwardedto data source 304, then dispatcher 312 also recalls the communication.In some embodiments, dispatcher 312 may be instructed to remain in stepmode and the client requested to resubmit the credentials and/or anothermechanism for authentication used. In some embodiments, other action(s)may be taken in response to MA being unsuccessful.

Using method 600 MFA may be provided for data source(s) 302 and/or 304in a data agnostic manner. Certain data sources, such as databasestypically do not support MFA. Thus, method 600 may provide additionalsecurity to such data sources without requiring changes to the code ofdata sources 302 and 304. Security of system 100 may thus be improved ina simple, cost effective manner.

FIG. 7 is a flow chart depicting an exemplary embodiment of method 700for performing federated identity management for a client for a datasource. Federated identity management allows end users to access variousfacilities in an organization, such as multiple databases, email,analytics or other applications, based on a group identity and using asingle set of credentials. For example, an end user may be a dataanalyst in a finance department. The end user may thus be considered amember of three groups: employees, data analysts and the financedepartment. A user identification and password for the end user mayallow the end user to access their company/employee email, applicationsfor the finance department, databases including information used by thefinance department such as financial projections for the organization,analytics applications accessible by data analysts and other data basedon the end user's membership in various groups within the organization.Federated identity management may use protocols such as lightweightdirectory access protocols (LDAP) and directories defining the groups towhich each end user belongs.

Method 700 is described in the context of system 300. However, method700 may be used in connection with other systems including but notlimited to systems 100 and 200. For simplicity, certain steps of method700 are depicted. Method 700 may include other and/or additional stepsand substeps. Further, the steps of method 700 may be performed inanother order including performing portions or all of some steps inparallel. In some embodiments, method 700 may be considered to be usedin implementing 506 of method 500. For the purposes of explanation,service 314-6 is considered to provide federated identity management.Method 700 may be considered to start after service 314-6 receives thecommunication from dispatcher 312.

Service 314-6 receives the end user's credentials, at 702. For example,dispatcher 312 forwards to service 314-6 a communication requestingaccess to data source 302. The communication may include the end user'suser identification and password for federated identity management. Inother embodiments, the end user credentials are otherwise associatedwith the communication but are provided to service 314-6. Service 314-6authenticates the end user with a federated identity management utilityor database 330-2, such as an LDAP directory, at 704. To authenticatethe end user the user identification and password are utilized. Service314-6 searches the federated identity management database 330-2 for thegroup(s) to which the end user belongs, at 706. Using one or more of thegroup(s) of which the user is a member, wrapper 310 logs onto the datasource 302 as a proxy for the end user, at 708. The end user may thenaccess data source 302 in accordance with the privilege and limitationsof the group(s) to which the end user belongs.

Using method 700, federated identity management can be achieved for datasource(s) 302 and/or 304. Some databases do not support federatedidentity management. Method 700 and wrapper 310 having data agnosticdispatcher 312 may allow for federated identity management for suchdatabases without changes to the databases. Thus, an end user may beable to access the desired data sources. Further, the organization canmanage access to the data sources using groups in the federated identitymanagement database. This may be achieved without requiring changes todata sources 302 and 304. Because wrapper 310 accesses data sources 302and/or 304 as a proxy for the end user, wrapper 310 may log activitiesof the end user. For example federated identity management service 314-6may store information related to queries performed by the end user aswell as the identity of the end user. Thus, despite using federatedidentity management to allow access to applications and data sourcesbased on groups, the organization may obtain visibility into theactivities of individual end users. In addition to improving ease ofadministration via federated identity management, improved informationand control over individuals' use of data sources 302 and 304 may beachieved.

FIG. 8 is a flow chart depicting an exemplary embodiment of method 800for performing federated identity management for a client for a datasource using an LDAP directory. Method 800 is described in the contextof system 300. However, method 800 may be used in connection with othersystems including but not limited to systems 100 and 200. Forsimplicity, certain steps of method 800 are depicted. Method 800 mayinclude other and/or additional steps and substeps. Further, the stepsof method 800 may be performed in another order including performingportions or all of some steps in parallel. In some embodiments, method800 may be considered to be used in implementing 506 of method 500and/or 704, 706 and/or 708 of method 700. For the purposes ofexplanation of method 800, service 314-6 is considered to providefederated identity management via LDAP. Method 800 is considered tocommence after wrapper 310 is provided with a specialized account forLDAP directory 330-2. The specialized account allows wrapper 310 toobtain information from LDAP directory 330-2 that is not available to atypical end user, such as the identification of end users and the groupsto which end users belong. In some embodiments, the account is a readonly account for wrapper 310.

Service 314-6 binds to the LDAP directory using the read only account at802. This may occur at some time before receipt of the end user'scredentials and the request to access a data source using federatedidentity management. The binding of service 314-6 with the LDAPdirectory allows service 314-6 to provide federated identity managementservices in some embodiments.

A communication requesting access to data source(s) 302 and/or 304 isreceived at dispatcher 310 and provided to service 314-6 in a manneranalogous to 502 and 504 of method 500. The communication includes theend user's LDAP credentials. Thus, the end user's LDAP credentials arereceived at service 314-6. After receiving the end user's LDAPcredentials, service 314-6 may search for the end user in the LDAPdirectory using the read only account, at 804. Searching LDAP directory330-2 allows service 314-6 to determine whether the user exists in LDAPdirectory 330-2. If not, wrapper 310 may prevent access to the desireddata source(s). If, however, the end user is found at 804, then service314-6 binds to the LDAP directory as a proxy for the end user, at 806.

Service 314-6 may then request a search for the groups to which the enduser belongs, at 808. This is facilitated by the read only account forwrapper 310. Thus, service 314-6 may determine the groups to which theend user belongs as well as the privileges and limitations on eachgroup. A group to be used for accessing the data source(s) 302 and/or304 is selected at 810. In some embodiments, service 314-6 ranks groupsbased upon their privileges. A group having more privileges (e.g. ableto access more data sources or more information on a particular datasource) is ranked higher. In some embodiments, service 314-6 selects thehighest ranked group for the end user. In some embodiments, service314-6 selects the lowest ranked group. In some embodiments, the user isallowed to select the group. In other embodiments, another selectionmechanism may be used.

The desired data source(s) are accessed using the selected group, at812. Thus, the end user may access data and/or applications based upontheir membership in the selected group. Information related to the enduser's activities is logged by wrapper 310, at 814. For example,services 314-6 may directly log the end user activities or may utilizeanother service, such as query analysis, to do so.

Using method 800, an end user may be able to access the desired datasources via federated identity management performed through an LDAPdirectory. The benefits of federated identity management may thus beachieved. In addition, the end user's actions may be logged. Thus,visibility into the activities of individual end users may be obtained.

FIG. 9 is a flow chart depicting an exemplary embodiment of method 900for analyzing and logging information related to queries of a datasource. Method 900 is described in the context of system 100. However,method 900 may be used in connection with other systems including butnot limited to systems 200 and 300. For simplicity, certain steps ofmethod 900 are depicted. Method 900 may include other and/or additionalsteps and substeps. Further, the steps of method 900 may be performed inanother order including performing portions or all of some steps inparallel. In some embodiments, method 900 may be considered to be usedin implementing 506 of method 500. For the purposes of explanation ofmethod 900, service 114-1 is considered to provide query analysis andlogging. Thus, a client, such as client 106-1 may be considered to beauthenticated for data source(s) 102 and/or 104 and to perform a queryfor data on one or both of data sources 102 and 104. In someembodiments, the query may be an SQL query.

Wrapper 110 receives an identification of information of interest in thedata source(s) 102 and/or 104, at 902. Also at 902, policies related tothe sensitive information are also received. Reception of thisinformation at 902 may be decoupled from receiving queries and analyzingqueries for the remainder of method 900. For example, owner(s) of datasource(s) 102 and/or 104 may indicated to wrapper 110 which tables,columns/rows in the tables, and/or entries in the tables includeinformation that is of interest or sensitive. For example, tablesincluding customer names, social security numbers (SSNs) and/or creditcard numbers (CCNs) may be identified at 902. Columns within the tablesindicating the SSN, CCN and customer name, and/or individual entriessuch as a particular customer's name, may also be identified at 902.This identification provides to wrapper 110 information which is desiredto be logged and/or otherwise managed. Further, policies related to thisinformation are provided at 902. Whether any logging is to be performedor limited is provided to wrapper at 902. For example, any user accessof customer tables may be desired to be logged. The policies indicatethat queries including such accesses are to be logged. Whether data suchas SSNs generated by a query of the customer table should be redactedfor the log may also be indicated in the policies.

Wrapper 110 receives a query from a client at dispatcher 112 andprovides the query to service 114-1, at 903. The query may also be sentfrom dispatcher 112 to the appropriate data source(s) as part of 903.Process 903 is analogous to 502 and 504 of method 500. Thus, the queryis received at service 114-1. Service 114-1 parses a query provided by aclient 106, at 904. For example, a client 106-1 may provide a query fordata source 102 to wrapper 110. Dispatcher 112 receives the query andprovides the query both to data source 102 and to service 114-1. Service114-1 parses the query to determine which operations are requested andon what portions of data source 102. Service 114-1 thus emits a logicalstructure describing the query and based on the parsing, at 906. In someembodiments, the logical structure is an abstract syntax treecorresponding to the query. Each node in the tree may represent a tablebeing searched, operation in the query, as well as information about theoperation. For example, a node may indicate a join operation or a searchoperation and be annotated with limitations on the operation.

The query is logged, at 908. The log may include the end user/client106-1 that provided the query as well as the query string. In addition,the features extracted from the abstract syntax tree may be logged in amanner that is indexable or otherwise more accessible to analytics.Further, the log may be configured to be human readable. In someembodiments, a JSON log may be used. For example, a list of theoperations and tables accessed in the query may be included in the log.Sensitive information such as SSN may be redacted from the log inaccordance with the identification of sensitive information and policiesrelating to sensitive information received at 902. Thus, a placeholdermay be provided in the log in lieu of the actual sensitive informationaccessed by the query. In some embodiments, the logical structure and/orlog are analyzed at 909. This process may include analyzing the abstractsyntax tree and/or information in the log.

Based on the query analysis and/or log, additional action may be takenby wrapper 110, at 910. For example, a query rewriting service that ispart of service 114-1 or a separate service may be employed if it isdetermined in 909 that the log generated in 908 indicates that the querymay adversely affect performance. For example, limits may be placed on aquery, clauses such as an “OR” clause and/or a tautology identifiedand/or removed. As a result, queries that result in too many rows beingreturned may be rewritten to reduce the number of rows. If the log orother portion of the query analysis indicates that the query mayrepresent an attack, then access to the data source may be denied at910. For example, the analysis at 909 of the logical structure and logmay indicate that the query includes wildcards or tautologies in users'names. The corresponding routine may terminate the connection to theclient from which the query originated. If the query has been passed onto data source 102, then the query may be canceled at 910. Unwantedexfiltration of sensitive information may thus be prevented. If thequery analysis indicates that a similar query was recently serviced,then some or all of the information for the similar query that alreadyexists in a cache may be used to service the query. If the query can becompletely serviced by information in the cache, then the query may berecalled from/canceled before or during servicing by data source 102.Thus, various actions may be taken based upon the analysis of the queryby service 114-1.

For example, suppose as mentioned above that data source 102 includes acustomer table of customer information having columns of customer names,customer SSNs, customer CCNs, tokenized CCNs (e.g. CCN encrypted withFPE or represented by a token), and customer identifiers (CIDs). Supposedata source 102 also includes an order table including a table ofcustomer orders. The table includes a column of order customeridentifiers (OCIDs) and multiple columns of orders for each customeridentifier. In each order column, the item prices for the order areindicated. The order customer identifier for the order table is the sameas the customer identifier in the customer table for data source 102.Query analysis and logging may be performed by service 114-1.

At 902, service 114-1 is informed that the customer table and thecolumns of customer names, customer SSNs and (tokenized) customer CCNsare sensitive information for which activity is desired to be logged.Also at 902, service 114-1 is informed that customer names and SSNs areto be redacted from the log. A query of data source 102 may be providedto dispatcher 112 by end user of client 106-1. Dispatcher 112 forwardsthe query to data source 102 and to service 114-1. The query is: selectobject price from customer table join order table on customeridentifier=order customer identifier and where name=John Smith (whereJohn is a name of a particular customer). Thus, the query determines theprice of objects ordered by John Smith. FIG. 10 depicts thecorresponding abstract syntax tree 1000 generated from the query at 906.The abstract syntax tree has been annotated for clarity. Nodes 1002,1004, 1012, 1022 and 1032 and lines connecting nodes 1002, 1004, 1012,1022 and 1032 represent the query. From abstract syntax tree 1002, a logis generated by service 114-1 at 908. The log indicates that thecustomer table has been accessed by end user of client 106-1, thatcolumn customer name was read, and the where name=[redacted] wasaccessed. This information may be provided in a format that is readilyusable by analytics, indexable and/or searchable. In some embodiments,the string forming the query may also be provided in the log. However,because they were not identified as being of interest, the order table,CID, OCID and object price are not included in the indexable portion ofthe log.

Thus, using method 900, performance of system 100 may be improved.Method 900 may facilitate analysis of queries performed, aid in responseto attacks, and/or improve performance of the data source. Becausedispatcher 110 is data agnostic and may be a transport layer component,this may be achieved without requiring changes to data sources 102 and104 while maintaining stability of the data sources 102 and 104. Thus,performance and security for system 100 may be enhanced.

FIGS. 11A and 11B are flow charts depicting exemplary embodiments ofmethods for utilizing tokenization and/or encryption of sensitive data.FIG. 11A is a flow chart depicting an exemplary embodiment of method1100 for using tokenization and/or encryption for storing data at a datasource. Method 1100 is described in the context of system 300. However,method 1100 may be used in connection with other systems including butnot limited to systems 100 and 200. For simplicity, certain steps ofmethod 1100 are depicted. Method 1100 may include other and/oradditional steps and substeps. Further, the steps of method 1100 may beperformed in another order including performing portions or all of somesteps in parallel. In some embodiments, method 1100 may be considered tobe used in implementing 506 of method 500.

Method 1100 may be considered to start after system 300 receivespolicies indicating how sensitive data are to be treated. For example,policies indicating what data are sensitive (e.g. which tables/entriesinclude sensitive data), what clients are allowed to have access to thesensitive data, for what purposes client(s) are allowed to have accessto the sensitive data, how the sensitive data are to be anonymized (e.g.tokenized and/or encrypted), and/or other information desired bycontroller of data sources 302 and/or 304 have already been received bywrapper 310 and provided to the appropriate service(s). Althoughdescribed in the context of access to a single data source, in someembodiments, method 1100 may be used for multiple data sources. In someembodiments, the same service fulfills request to store sensitive dataand requests to obtain sensitive data. In some embodiments, someservice(s) may service requests to store data/tokenize data while otherservice(s) are used obtain the tokenized data. However, such servicescommunicate in order to service at least some of the requests. In someembodiments, the same service may utilize different types ofanonymization (e.g. tokenization and encryption). In other embodiments,different services may be used for different types of anonymization. Forexample, one service may tokenize data while another service encryptsdata. Method 1100 is described as being used in connection with method1150. In other embodiments, method 1100 may be used with a differentmethod for accessing encrypted/tokenized data.

A request from a client to store sensitive data at a data source isreceived by a wrapper, at 1102. The dispatcher, which is data agnostic,forwards the request to an encryption/tokenization service foranonymization of the sensitive data desired to be stored, at 1104. Basedon the policies provided and/or capabilities of the services, thesensitive data is and anonymized, at 1106. In some embodiments, the datadesired to be stored includes sensitive data desired to be anonymized aswell as data that need not by anonymized. In such embodiments, 1106 alsoincludes identifying the sensitive data to be anonymized. In someembodiments, anonymizing data includes encrypting and/or tokenizing thedata. For some sensitive data, encryption such as format preservingencryption (FPE) may be used. For example, CCNs and SSNs may beencrypted using FPE such that the encrypted data has the same number ofdigits as the CCN and SSN (i.e. such that the format is preserved) butdoes not have intrinsic meaning. The alphanumeric string having ninemembers may replace an SSN. Other types of encryption, tokenization,and/or data masking may also be used at 1106. Thus, at 1106 thesensitive data is anonymized. Because policies may be used to determinehow and what data are encrypted/tokenized, 1106 is performed on anattribute level. For example, the CCN of a user may be encrypted by FPE,but the SSN of the same user may be replaced by a token based on thepolicies used by the encryption/tokenization service. The anonymizeddata is stored in the data source, at 1108. Thus, the anonymized datamay be retained in place of the actual sensitive data. In someembodiments, the sensitive data may also be stored, for example in asecure data vault, which may require enhanced authentication to access.Thus, using method 1100, sensitive data may be tokenized and/orencrypted and stored using a data agnostic dispatcher.

FIG. 11B is a flow chart depicting an exemplary embodiment of method1150 for accessing tokenized and/or encrypted data from a data source.Method 1150 is described in the context of system 300. However, method1150 may be used in connection with other systems including but notlimited to systems 100 and 200. For simplicity, certain steps of method1150 are depicted. Method 1150 may include other and/or additional stepsand substeps. Further, the steps of method 1150 may be performed inanother order including performing portions or all of some steps inparallel. In some embodiments, method 1150 may be considered to be usedin implementing 506 of method 500. Method 1150 may be considered tostart after system 300 receives policies indicating how sensitive dataare to be treated. For example, policies indicating what data aresensitive (e.g. which tables/entries include sensitive data), whatclients are allowed to have access to the sensitive data, for whatpurposes client(s) are allowed to have access to the sensitive data, howthe sensitive data are to be anonymized (e.g. tokenized and/orencrypted), and/or other information desired by controller of datasources 302 and/or 304 have already been received by wrapper 310 andprovided to the appropriate service(s). Although described in thecontext of access to a single data source, in some embodiments, method1150 may be used for multiple data sources. In some embodiments, thesame service fulfills request to store sensitive data and requests toobtain sensitive data. In some embodiments, some service(s) may servicerequests to store data/tokenize data while other service(s) are usedobtain the tokenized data. However, such services communicate in orderto service at least some of the requests. In some embodiments, the sameservice may utilize different types of anonymization (e.g. tokenizationand encryption). In other embodiments, different services may be usedfor different types of anonymization. For example, one service maytokenize data while another service encrypts data. Method 1150 isdescribed as being used in connection with method 1100. In otherembodiments, method 1150 may be used with a different method foranonymizing data.

A request for the sensitive data stored at data source is received bythe wrapper, at 1152. The request may come from the same client thatstored the data or a different client. Because request(s) for data maybe independent of storage, 1152 through 1162 may be decoupled from 1102through 1108. For example, the request may be received at 1152 at adifferent time, or may not be received. Thus, methods 1100 and 1150 areseparately described. The dispatcher provides the request to accesssensitive data to encryption/tokenization service, at 1154. The requestmay also be forwarded to the data source storing the anonymized data.

The encryption/tokenization service determines what type ofauthorization the requestor possesses, at 1156. The requester may onlybe authorized to receive the anonymized (e.g. tokenized/encrypted) data.For example, the requesting client might be a computer system of datascientist associated with system 300. The data scientist/client may beallowed to track use of a credit card number, but not be authorized toknow the actual credit card number. The requester may be authorized toreceive the original, sensitive data. For example, the requesting clientmight be a merchant's payment system or the original user's computersystems, both of which may be authorized to receive the de-anonymized(e.g. unencrypted/de-tokenized) sensitive data. However, the requestermay be unauthorized to receive either data. For example, the requestingclient might be a malicious individual attempting to steal the sensitivedata. At 1156, therefore, the encryption/tokenization service validatescredentials for the requesting client. The encryption/tokenizationservice may use passwords, certificates, multifactor authentication,behavioral baselining through collector(s) and/or other mechanism(s).Thus, encryption/tokenization service may call another service toperform authentication at 1156.

If the requesting client is determined to be authorized to receive thesensitive data, then the anonymized data stored at the data source isretrieved, de-anonymized and provided to client, at 1158. For example,encryption/tokenization service may decrypt and/or detokenize the datathat was stored in the data source. In another embodiment, instead of orin addition to decrypting/detokenizing the data, encryption/tokenizationservice may retrieve the original, sensitive data from a secure datavault (not shown in FIGS. 3 and 11A-11B). The sensitive data is thensent to the authorized requester at 1158.

If the requesting client is determined to be authorized to receive onlythe anonymized data, then this anonymized data are retrieved and sent tothe requester, at 1160. For example, encryption/tokenization service maysimply retrieve the anonymized data from the data source and forwardthis data to the requesting client. In some embodiments, a requester maybe authorized to receive either or both of the sensitive data and theanonymized data. In such embodiments, 1158 and/or 1160 may includedetermining whether the requester has selected theanonymized/de-anonymized data and providing the anonymized/de-anonymizeddata. In some embodiments, both the anonymized and the de-anonymizeddata might be provided.

If, however, it is determined that the requester was not authorized,then other action is taken at 1162. For example, the routine mayterminate the connection to client as described above, the communicationmay be recalled from the data source, the client may be blacklisted,managers of system 300 and/or owner of the sensitive data may benotified of the attempted breach and/or other action taken. For example,as discussed above, the corresponding routine may terminate theconnection to the client from which the query originated. If the queryhas been passed on to the data source, then the query may be canceled at1162. Unwanted exfiltration of sensitive information may thus beprevented.

Although described in the context of anonymized data at 1106 and storingthe anonymized data at 1108, in another embodiment, step 1106 might beskipped and the sensitive data stored at 1108. However, in suchembodiments, at 1158 no decryption is performed for the requesterdetermined to be authorized to receive the sensitive data. Further, forrequesters determined to be authorized to receive onlyencrypted/tokenized data, the data are encrypted/tokenized and thenprovided at 1160. Thus, methods 1100 and 1150 may be adapted to the casewhere sensitive data are stored.

For example, a request from client 306-1 to store sensitive data at datasource 302 may be received by wrapper 310, at 1102. Dispatcher 312forwards the request to encryption/tokenization service 314-2 foranonymization, at 1104. Based on the policies provided and/orcapabilities of encryption/tokenization service 314-2, the sensitivedata is identified and anonymized, at 1106. For example,encryption/tokenization service 314-2 may encrypt some sensitive dataand tokenize other sensitive data. The anonymized data is stored in datasource 302, at 1108.

A request from client 306-2 for the sensitive data stored at the datasource is received by the wrapper 310, at 1152. Dispatcher 310 providesthe request to access sensitive data to encryption/tokenization service314-2, at 112. The request may also be forwarded by dispatcher 312 todata source 302.

Encryption/tokenization service 314-2 determines what type ofauthorization the requestor possesses, at 1156. Thus,encryption/tokenization service 314-2 validates credentials for therequesting client 306-2.

If the requesting client 306-2 is determined to be authorized to receivethe sensitive data, then the anonymized data stored at data source 302is retrieved, decrypted/detokenized and provided to client 306-2, at1158. In another embodiment, instead of or in addition todecrypting/detokenizing the data, encryption/tokenization service 314-2may retrieve the original, sensitive data from a secure data vault. Thesensitive data is then sent to the authorized requester. If therequesting client 306-2 is determined to be authorized to receive onlythe anonymized data, then encryption/tokenization service 314-2retrieves the anonymized data from data source 302 and forwards thisdata to the requesting client 306-2. If, however, it is determined thatthe requester was not authorized, then the routine may terminate theconnection to client 306-2, the communication may be canceled orrecalled from data source 302, client 306-2 may be blacklisted, managersof system 300 and/or owner of the sensitive data (e.g. user of client306-1) may be notified of the attempted breach and/or other actiontaken.

Using methods 1100 and 1150 sensitive data may be more securely storedand retrieved. Instead of storing sensitive data, anonymized data may bestored at 1108. How and what data are anonymized may be determined on anattribute level, which improves flexibility of methods 1100 and 1150.This improves the ability of system 300 and methods 1100 and 1150 toprotect sensitive data from being inappropriately accessed. Becausethese functions are provided via service(s) 314, the enhanced securitymay be provided for data source(s) 302 and/or 304 that do not otherwisesupport encrypted data. Stated differently, secure storage andencryption/tokenization of data may be performed in a data agnosticmanner. Thus, methods 1100 and 1150 may provide additional security tosuch data sources without requiring changes to the code of data sources302 and 304. Security may thus be improved in a simple, cost effectivemanner.

FIGS. 12A and 12B are flow charts depicting exemplary embodiments ofmethods for providing client information and for performing behavioralbaselining for clients. FIG. 12A is a flow chart depicting an exemplaryembodiment of method 1200 for providing client information and may beused as part of performing behavioral baselining for a client. Method1200 is described in the context of system 300. However, method 1200 maybe used in connection with other systems including but not limited tosystems 100 and 200 that employ collectors such as collectors 320. Forsimplicity, certain steps of method 1200 are depicted. Method 1200 mayinclude other and/or additional steps and substeps. Further, the stepsof method 1200 may be performed in another order including performingportions or all of some steps in parallel. In some embodiments, method1200 may be considered to be used in implementing 506 of method 500.Method 1200 is described in the context of clients 306-2 and 306-3,collectors 320-2 and 320-3, service 314-2 and data source 302. Thus,method 1200 commences after collectors 320 have been provided on one ormore clients 306 utilizing data sources. However, in other embodiments,other clients, collectors, service(s) and/or other data sources may beused.

Communications for data source(s) to be issued by a client areintercepted, for example by a collector at the client, at 1202. In someembodiments, queries, method or API calls, commands or other messagesmay be intercepted before being provided from the client fortransmission to the wrapper. In some embodiments, for example, acollector may attach itself to a client application and use JavaDatabase Connectivity (JDBC) to intercept queries from the client of thedata source(s). Thus, the collectors monitor the corresponding clientsand intercept particular calls.

The state of the client issuing the communication is determined andattached to/associated with the intercepted communication, at 1204. Forexample, the type of call, the type of session/session identification,user identification for the session, the type of command (e.g. get, put,post, and delete commands), APIs, IP address, query attributes, methodcalls, order of queries, and/or application making the calls may bedetected by the collector and attached to the communication at 1204.These attributes represent the context, or state, of the client (orclient application) when issuing the communication. The collectorattaches this context/state to the query or other communication beingprovided from the client. The communication and attached state are sentfrom the client, at 1206. In some embodiments, the attached state may beconsidered to be part of or included in the communication sent from theclient.

In some embodiments, other clients may receive the communication fromthe sending client, perform other functions and then issue anothercommunication. Thus, multiple clients may send and receive acommunication before the communication is provided to the wrapper ordata source. At each client that includes a collector and that receivesthe communication, any outgoing communication is intercepted as in 1202,the context for that client is determined and attached to thecommunication as in 1204 and the communication and state/context sent asin 1206, via 1208. If only a single client having a collector sends thecommunication to the wrapper, then 1208 may be omitted. If five clientshaving collectors send the communication in series, then the originatingclient performs 1202, 1204 and 1206. 1208 may be repeated four times forthe four additional clients receiving and sending the communication. Iffive clients, only four of which have collectors, receive thecommunication in series, then 1208 may be repeated three times. Thus,multiple clients may be involved in providing a communication to thedata source. Each of the clients having a collector can attach theirstate to the communication. Further, the states may be attached in theorder in which the clients sent/received the communication. The lastclient sending the communication provides the communication to awrapper, such as wrapper 310.

Thus, using method 1200, the context for a client can be provided toalong with the communication. For clients providing multiplecommunications, the series of contexts provided with thesecommunications may represent typical behavior for the client duringinteraction with the data source. Thus, the client(s) may sendinformation relating to their state and/or behavior in addition tocommunications such as queries.

FIG. 12B is a flow chart depicting an exemplary embodiment of method1250 for performing behavioral baselining for a client. Method 1250 isdescribed in the context of system 300. However, method 1250 may be usedin connection with other systems including but not limited to systems100 and 200 that employ collectors such as collectors 320. Forsimplicity, certain steps of method 1250 are depicted. Method 1250 mayinclude other and/or additional steps and substeps. Further, the stepsof method 1250 may be performed in another order including performingportions or all of some steps in parallel. In some embodiments, method1250 may be considered to be used in implementing 506 of method 500.Method 1250 is described in the context of clients 306-2 and 306-3,collectors 320-2 and 320-3, service 314-2 and data source 302. Thus,method 1250 commences after collectors 320 have been provided on one ormore clients 306 utilizing data sources. However, in other embodiments,other clients, collectors, service(s) and/or other data sources may beused. Method 1250 may be performed in conjunction with method 1200 andso may receive communications and states/contexts provided via method1200.

The communication and context(s) of the client(s) are received at thewrapper, at 1252. The wrapper thus receives the communication, which mayinclude multiple queries or method calls, as well as the states of allclients having collectors which sent the communication along beforereaching the wrapper. In some embodiments, the communication andattached context(s) are received at the dispatcher. In some embodiments,the communication and attached context sent by the client at 1206 or1208 of method 1200 is received at the wrapper at 1252.

The context(s) are forwarded from the dispatcher to behavioralbaselining service(s), at 1254. In some embodiments, the communicationswith which the context(s) are associated are also provided to thebehavioral baselining service(s) at 1254. Also at 1254, the dispatchermay send the communication on to the desired data source(s). Thus,processing of the query or other calls in the communication may not bedelayed by inspection of the context(s) of clients and other functionsperformed by behavioral baselining service(s). In other embodiments, thecommunication may be held at the dispatcher until behavioral baseliningis completed. This may occur, for example, if the dispatcher is in stepmode described above.

The state(s)/context(s) for the client(s) associated with thecommunication are compared with baseline(s) for client(s), at 1256. Insome embodiments, the communication is also part of this comparison. Forexample, the particular query of the database provided by the client aswell as the state of the client may be used for comparison with thebaseline. In other embodiments, just the context(s) might be used. Insome embodiments, a single context of a client associated with a singlecommunication is compared to the baseline(s) at 1256. In otherembodiments, multiple contexts that may be in a particular order of aclient are compared to the baseline at 1256. For example, the behavioralbaselining service may store the context received for each communicationfor each client having a collector. Frequently, a client issues multiplecommunications for a data source when utilizing the data source. A setof these contexts for a particular client represents the behavior ofthat client around the time the client interacts with the data source.The behavioral baselining service analyzes the behavior (series ofcontexts) of the client(s) providing the communication(s). In someembodiments, only the identities of the contexts are used. In someembodiments, the identities of the contexts as well as their order areused for comparison. In some embodiments, the behavioral baseliningservice compares the context(s) to the behavior based upon a model ofthe behavior (the series of states/contexts), such as a Hidden MarkovModel. Thus, in 1256 the behavioral baselining service maintains a modelof requesting client(s)′ behavior and compares the context in thecurrent communication to the behavior. In some embodiments, a singlecontext may be compared to the baseline in some cases and behavior inothers. For example, for a first communication received by the wrapper,that first communication may be compared to the baseline. As additionalcommunications are received, these communications may be compared to thebaseline at 1256. In other embodiments, a client might first beauthenticated and granted access to a data source based on anothermethod of authentication, such as MFA. Once the client sends additionalcommunication(s) with additional context(s), these communication(s) andcontext(s) may be used to compare the behavior for the client with thebaseline. In some embodiments, the initial communication andauthentication may be considered part of the behavior. In otherembodiments, the initial communication and authentication may beconsidered separately from subsequent communication(s) and state(s).

If the context(s) for the current communication(s) sufficiently matchthe behavior, then the requesting client(s) are allowed access to thedata source, at 1258. Thus, the data source is allowed to service thecommunication(s) provided by the client(s). If it is determined in 1256that the context does not sufficiently match the behavior, then thedesired action is taken, at 1260. In some embodiments, the action takenmay depend upon the mismatch determined in 1256 or on other factors. Forexample, the client(s) initiating the communication(s) may not beallowed to access the data source. In such cases, the dispatcher may beinformed and the corresponding routine used to terminate the connectionto client(s). If the communication had already been forwarded to thedata source(s), then the communication may be recalled from the datasource(s). If the client had previously been authenticated, then theauthentication may be revoked. In such embodiments, the dispatcher maybe informed the client is unauthorized and the corresponding routineused to terminate the connection to client(s). Communication(s) that hadbeen forwarded to the data source(s) may also be recalled from the datasource(s). If the mismatch is sufficiently great or occurs greater thana threshold number of times, or at least a particular number of times ina row, then the client(s) may be blacklisted. In some embodiments, asecondary mechanism of authentication, such as MFA, may be invoked at1260. Thus, access to the data source(s) may be determined at least inpart based upon behavior of the requesting client(s). These and/or otheractions may be taken at 1260.

The model/baseline may be updated, at 1262. For example, if it isdetermined that the context sufficiently matches the behavior at 1258,then the model/baseline may be updated with the context in thecommunication from client(s). If the context is considered inconsistentwith the baseline, then the model/baseline may be updated with thisinformation.

For example, suppose collector 320-2 in client 306-2 intercepts acommunication including a query of data source 302 at 1202. The contextof client 306-2 is determined by collector 320-2 and attached to thequery. Client 306-2 then provides the communication and context towrapper 310. Because client 306-2 provides the communication to wrapper310 without providing the communication to another client 306, 1208 isskipped. Dispatcher 312 receives the communication at 1252 and providesthe communication and context to behavioral baselining service 314-2 at1254. The communication is also passed to data source 302 at 1254.Behavioral baselining service 314-2 compares the context received at1254 to the baseline for client 306-2 at 1256. If the context receivedis consistent with the baseline, then access is allowed to data source302, at 1258. Otherwise, access may be denied, for example theconnection terminated, at 1260. Additional actions may also be taken at1260 such as blacklisting client 306-2. The baseline may also be updatedat 1262.

In some cases, multiple applications in multiple clients may pass acommunication before the communication is sent to a data source. Forexample, this may occur where microservices are employed, as discussedabove. For example, suppose collector 320-2 in client 306-2 interceptsthe communication including a query of data source 302 at 1202. Thestate of client 306-2 is determined by collector 320-2 and attached tothe query. Client 306-2 then provides the communication and state toclient 306-3. In some cases, client 306-3 may add another query to thecommunication or otherwise modify the communication. Collector 320-3 inclient 306-3 intercepts the communication, attaches the state of client306-3 and provides the communication to wrapper 310 at 1208. Thus, thecommunication now includes the states of clients 306-2 and 306-3. Ifclient 306-2 or 306-2 had passed the communication to client 306-4,which does not include a collector, then 1208 would be skipped forclient 306-4 because no collector is present to determine and attach thestate of client 306-4 to the communication. Dispatcher 312 receives thecommunication at 1252 and provides the communication and states tobehavioral baselining service 314-2 at 1254. The communication is alsopassed to data source 302 at 1254. Behavioral baselining service 314-2compares the states received at 1254 to the baselines for clients 306-2and 306-3 at 1256. If the states received are consistent with thebaselines, then access is allowed to data source 302, at 1258.Otherwise, access may be denied, for example the connection terminatedand the communication recalled from data source 302, at 1260. Additionalactions may also be taken at 1260 such as blacklisting client 306-2and/or 306-3. The baseline(s) may also be updated at 1262.

Using methods 1200 and 1250, security and performance for data sourcesmay be improved. The context(s)/state(s) of client(s) in communicationsrequesting access to data source(s) may be analyzed to determine whetherthe communication is consistent with previous behavior of client(s). Ifthe state(s) of the client(s) are inconsistent with the baseline, thenaccess to the data source(s) may be prevented and/or additional actiontaken. Methods 1200 and 1250 may also be extended to compare behavior (aseries of states, for example for multiple queries) of clients toprevious behavior and authenticate clients based upon their behavior.Thus, attacks from a client that has been hijacked may be detected andaddressed. Further, collectors need not be present on all clients toenhance security. Instead, if a sufficiently high fraction of clientsinclude collectors, data sources may be protected in a manner akin toherd immunity. Methods 1200 and/or 1250 may be coupled with othermethods, such as query analysis in method 900, authentication usingmethod 400, tokenization in method 1100 and/or MFA in method 600 tofurther improve security.

As indicated above, various services may be combined. For example,wrapper 310 may provide multifactor authentication and/or federatedidentity management via service 314-1, query analysis via service 314-2,query rewriting via service 314-3 (or as part of service 314-2),behavioral baselining via service 314-4, tokenization of sensitive datavia service 314-5, and/or other service other functionality via service314-6. In such embodiments, dispatcher 312 may forward some or all ofthe request to multiple services 314 and/or services 314 may communicatewith other services in order to perform the desired functions. Thus,performance of and security for data sources 302 and/or 304 may beimproved by a variety of services without altering data sources 302and/or 304. Moreover, new services may be added to wrapper 310 for datasource(s) 302 and/or 304 by adding service module or updating services314. These new services may be added without altering the code of datasources 302 and 304. Thus, performance, security and/or other featuresof system 300 can continue to be improved.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A method, comprising: receiving a communicationfor a data source at a wrapper, the wrapper including a dispatcher and aservice, the dispatcher receiving the communication and being dataagnostic, the communication corresponding to end user credentials for anend user; providing the communication from the dispatcher to the datasource and to the service; and authenticating, using the service, theend user based on the end user credentials and utilizing federatedidentity management.
 2. The method of claim 1, further comprising:accessing the data source by the wrapper as a proxy for the end user ifthe end user is authenticated using the federated identity management.3. The method of claim 2, further comprising: logging end useractivities for the data source.
 4. The method of claim 1, wherein theauthenticating further includes: providing the end user credentials to afederated identity management data source; the method further comprisingsearching the federated identity management data source for at least onegroup to which the end user belongs.
 5. The method of claim 4, furthercomprising: performing a read only binding of the service to thefederated identity management data source; wherein the authenticatingfurther includes searching the federated identity management data sourcefor the end user using the read only binding.
 6. The method of claim 5,further comprising: binding the service to the federated identitymanagement data source as a proxy for the end user if the end user isauthenticated.
 7. The method of claim 1 further comprising: preventingaccess to the data source if the end user is not authenticated utilizingthe federated identity management:
 8. A system, comprising: a processorconfigured to: receive a communication for a data source at a wrapper,the wrapper including a dispatcher and a service, the dispatcherreceiving the communication and being data agnostic, the communicationcorresponding to end user credentials for an end user; provide thecommunication from the dispatcher to the data source and to the isservice; and authenticate, using the service, the end user based on theend user credentials and utilizing federated identity management; and amemory coupled to the processor and configured to provide the processorwith instructions.
 9. The system of claim 8, wherein the processor isfurther configured to: access the data source by the wrapper as a proxyfor the end user if the end user is authenticated using the federatedidentity management.
 10. The system of claim 9, wherein the processor isfurther configured to: log end user activities for the data source. 11.The system of claim 8, wherein to authenticate the end user theprocessor is further configured to: provide the end user credentials toa federated identity management data source; and wherein the processoris further configured to search the federated identity management datasource for at least one group to which the end user belongs.
 12. Thesystem of claim 11, wherein the processor is further configured to:perform a read only binding of the service to the federated identitymanagement data source; wherein to authenticating the end user theprocessor is further configured to search the federated identitymanagement data source for the end user using the read only binding. 13.The system of claim 12, wherein the processor is further configured to:bind the service to the federated identity management data source as aproxy for the end user if the end user is authenticated.
 14. The systemof claim 8 wherein the processor is further configured to: preventaccess to the data source if the end user is not authenticated utilizingthe federated identity management:
 15. A computer program product, thecomputer program product being embodied in a tangible computer readablestorage medium and comprising computer instructions for: receiving acommunication for a data source at a wrapper, the wrapper including adispatcher and a service, the dispatcher receiving the communication andbeing data agnostic, the communication corresponding to end usercredentials for an end user; providing the communication from thedispatcher to the data source and to the service; and authenticating,using the service, the end user based on the end user credentials andutilizing federated identity management.
 16. The computer programproduct of claim 15, wherein the computer instructions further includecomputer instructions for: accessing the data source by the wrapper as aproxy for the end user if the end user is authenticated using thefederated identity management.
 17. The computer program product of claim16, wherein the computer instructions further include computerinstructions for: logging end user activities for the data source. 18.The computer program product of claim 15, wherein the computerinstructions for authenticating further include computer instructionsfor: providing the end user credentials to a federated identitymanagement data source; the method further comprising searching thefederated identity management data source for at least one group towhich the end user belongs.
 19. The computer program product of claim18, wherein the computer instructions further include computerinstructions for: performing a read only binding of the service to thefederated identity management data source; wherein the authenticatingfurther includes searching the federated identity management data sourcefor the end user using the read only binding.
 20. The computer programproduct of claim 19, wherein the computer instructions further includecomputer instructions for: binding the service to the federated identitymanagement data source as a proxy for the end user if the end user isauthenticated.